Skip to content

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #30249

/assign sdodson

…s sent via telemetry from each cluster

In 4.20 techpreview, more series are to be sent to telemetry, compared
to a 4.19 techpreview:

ALERTS{}	12					      |	ALERTS{}	9
apiserver_list_watch_request_success_total:rate:sum{}	2	apiserver_list_watch_request_success_total:rate:sum{}	2
cco_credentials_mode{}	1					cco_credentials_mode{}	1
cluster:alertmanager_integrations:max{}	1			cluster:alertmanager_integrations:max{}	1
cluster:apiserver_current_inflight_requests:sum:max_over_time	cluster:apiserver_current_inflight_requests:sum:max_over_time
cluster:capacity_cpu_cores:sum{}	2			cluster:capacity_cpu_cores:sum{}	2
cluster:capacity_memory_bytes:sum{}	2			cluster:capacity_memory_bytes:sum{}	2
cluster:console_auth_login_failures_total:sum{}	1	      <
cluster:console_auth_login_requests_total:sum{}	1	      <
cluster:console_auth_login_successes_total:sum{}	3     <
cluster:console_auth_logout_requests_total:sum{}	1     <
cluster:console_customization_perspectives_info:max{}	1     <
cluster:console_plugins_info:max{}	2		      <
cluster:controlplane_topology:info{}	1			cluster:controlplane_topology:info{}	1
cluster:cpu_usage_cores:sum{}	1				cluster:cpu_usage_cores:sum{}	1
cluster:infrastructure_topology:info{}	1			cluster:infrastructure_topology:info{}	1
cluster:ingress_controller_aws_nlb_active:sum{}	1		cluster:ingress_controller_aws_nlb_active:sum{}	1
cluster:kube_persistentvolume_plugin_type_counts:sum{}	1	cluster:kube_persistentvolume_plugin_type_counts:sum{}	1
cluster:kube_persistentvolumeclaim_resource_requests_storage_	cluster:kube_persistentvolumeclaim_resource_requests_storage_
cluster:kubelet_volume_stats_used_bytes:provisioner:sum{}	cluster:kubelet_volume_stats_used_bytes:provisioner:sum{}
cluster:memory_usage_bytes:sum{}	1			cluster:memory_usage_bytes:sum{}	1
cluster:network_attachment_definition_enabled_instance_up:max	cluster:network_attachment_definition_enabled_instance_up:max
cluster:network_attachment_definition_instances:max{}	17	cluster:network_attachment_definition_instances:max{}	17
cluster:node_instance_type_count:sum{}	2			cluster:node_instance_type_count:sum{}	2
cluster:openshift_route_info:tls_termination:sum{}	3	cluster:openshift_route_info:tls_termination:sum{}	3
cluster:ovnkube_controller_admin_network_policies_db_objects:	cluster:ovnkube_controller_admin_network_policies_db_objects:
cluster:ovnkube_controller_admin_network_policies_rules:max{}	cluster:ovnkube_controller_admin_network_policies_rules:max{}
cluster:ovnkube_controller_baseline_admin_network_policies_db	cluster:ovnkube_controller_baseline_admin_network_policies_db
cluster:ovnkube_controller_baseline_admin_network_policies_ru	cluster:ovnkube_controller_baseline_admin_network_policies_ru
cluster:ovnkube_controller_egress_routing_via_host:max{}	cluster:ovnkube_controller_egress_routing_via_host:max{}
cluster:route_metrics_controller_routes_per_shard:avg{}	1	cluster:route_metrics_controller_routes_per_shard:avg{}	1
cluster:route_metrics_controller_routes_per_shard:max{}	1	cluster:route_metrics_controller_routes_per_shard:max{}	1
cluster:route_metrics_controller_routes_per_shard:median{}	cluster:route_metrics_controller_routes_per_shard:median{}
cluster:route_metrics_controller_routes_per_shard:min{}	1	cluster:route_metrics_controller_routes_per_shard:min{}	1
cluster:telemetry_selected_series:count{}	1		cluster:telemetry_selected_series:count{}	1
cluster:usage:containers:sum{}	1				cluster:usage:containers:sum{}	1
cluster:usage:ingress_frontend_bytes_in:rate5m:sum{}	1	cluster:usage:ingress_frontend_bytes_in:rate5m:sum{}	1
cluster:usage:ingress_frontend_bytes_out:rate5m:sum{}	1	cluster:usage:ingress_frontend_bytes_out:rate5m:sum{}	1
cluster:usage:ingress_frontend_connections:sum{}	1	cluster:usage:ingress_frontend_connections:sum{}	1
cluster:usage:kube_node_ready:avg5m{}	1			cluster:usage:kube_node_ready:avg5m{}	1
cluster:usage:kube_schedulable_node_ready_reachable:avg5m{}	cluster:usage:kube_schedulable_node_ready_reachable:avg5m{}
cluster:usage:openshift:ingress_request_error:fraction5m{}	cluster:usage:openshift:ingress_request_error:fraction5m{}
cluster:usage:openshift:ingress_request_total:irate5m{}	1	cluster:usage:openshift:ingress_request_total:irate5m{}	1
cluster:usage:openshift:kube_running_pod_ready:avg{}	1	cluster:usage:openshift:kube_running_pod_ready:avg{}	1
cluster:usage:resources:sum{}	335			      |	cluster:usage:resources:sum{}	331
cluster:usage:workload:capacity_physical_cpu_core_seconds{}	cluster:usage:workload:capacity_physical_cpu_core_seconds{}
cluster:usage:workload:capacity_physical_cpu_cores:max:5m{}	cluster:usage:workload:capacity_physical_cpu_cores:max:5m{}
cluster:usage:workload:capacity_physical_cpu_cores:min:5m{}	cluster:usage:workload:capacity_physical_cpu_cores:min:5m{}
cluster:usage:workload:ingress_request_error:fraction5m{}	cluster:usage:workload:ingress_request_error:fraction5m{}
cluster:usage:workload:ingress_request_total:irate5m{}	1	cluster:usage:workload:ingress_request_total:irate5m{}	1
cluster:usage:workload:kube_running_pod_ready:avg{}	1	cluster:usage:workload:kube_running_pod_ready:avg{}	1
cluster:virt_platform_nodes:sum{}	2			cluster:virt_platform_nodes:sum{}	2
cluster:volume_manager_selinux_volumes_admitted_total{}	1	cluster:volume_manager_selinux_volumes_admitted_total{}	1
cluster_feature_set{}	1					cluster_feature_set{}	1
cluster_infrastructure_provider{}	1			cluster_infrastructure_provider{}	1
cluster_installer{}	1					cluster_installer{}	1
cluster_legacy_scheduler_policy{}	1			cluster_legacy_scheduler_policy{}	1
cluster_master_schedulable{}	1				cluster_master_schedulable{}	1
cluster_operator_conditions{}	165			      |	cluster_operator_conditions{}	164
cluster_operator_up{}	36					cluster_operator_up{}	36
cluster_version_capability{}	17				cluster_version_capability{}	17
cluster_version_payload{}	2				cluster_version_payload{}	2
cluster_version{}	4					cluster_version{}	4
code:apiserver_request_total:rate:sum{}	16		      |	code:apiserver_request_total:rate:sum{}	17
console_url{}	1						console_url{}	1
count:up1{}	78					      |	count:up0{}	1
							      >	count:up1{}	77
csv_succeeded{}	2						csv_succeeded{}	2
imageregistry:imagestreamtags_count:sum{}	4		imageregistry:imagestreamtags_count:sum{}	4
imageregistry:operations_count:sum{}	4			imageregistry:operations_count:sum{}	4
insightsclient_request_send_total{}	1			insightsclient_request_send_total{}	1
instance:etcd_disk_backend_commit_duration_seconds:histogram_	instance:etcd_disk_backend_commit_duration_seconds:histogram_
instance:etcd_disk_wal_fsync_duration_seconds:histogram_quant	instance:etcd_disk_wal_fsync_duration_seconds:histogram_quant
instance:etcd_mvcc_db_total_size_in_bytes:sum{}	3		instance:etcd_mvcc_db_total_size_in_bytes:sum{}	3
instance:etcd_mvcc_db_total_size_in_use_in_bytes:sum{}	3	instance:etcd_mvcc_db_total_size_in_use_in_bytes:sum{}	3
instance:etcd_network_peer_round_trip_time_seconds:histogram_	instance:etcd_network_peer_round_trip_time_seconds:histogram_
instance:etcd_object_counts:sum{}	9			instance:etcd_object_counts:sum{}	9
monitoring:container_memory_working_set_bytes:sum{}	1	monitoring:container_memory_working_set_bytes:sum{}	1
monitoring:haproxy_server_http_responses_total:sum{}	2	monitoring:haproxy_server_http_responses_total:sum{}	2
namespace_job:scrape_samples_post_metric_relabeling:topk3{}	namespace_job:scrape_samples_post_metric_relabeling:topk3{}
namespace_job:scrape_series_added:topk3_sum1h{}	3		namespace_job:scrape_series_added:topk3_sum1h{}	3
node_role_os_version_machine:cpu_capacity_cores:sum{}	2	node_role_os_version_machine:cpu_capacity_cores:sum{}	2
node_role_os_version_machine:cpu_capacity_sockets:sum{}	2	node_role_os_version_machine:cpu_capacity_sockets:sum{}	2
olm_resolution_duration_seconds{}	3			olm_resolution_duration_seconds{}	3
openshift:cpu_usage_cores:sum{}	1				openshift:cpu_usage_cores:sum{}	1
openshift:memory_usage_bytes:sum{}	1			openshift:memory_usage_bytes:sum{}	1
openshift:openshift_network_operator_ipsec_state:info{}	1	openshift:openshift_network_operator_ipsec_state:info{}	1
openshift:prometheus_tsdb_head_samples_appended_total:sum{}	openshift:prometheus_tsdb_head_samples_appended_total:sum{}
openshift:prometheus_tsdb_head_series:sum{}	1		openshift:prometheus_tsdb_head_series:sum{}	1
os_image_url_override:sum{}	1				os_image_url_override:sum{}	1
profile:cluster_monitoring_operator_collection_profile:max{}	profile:cluster_monitoring_operator_collection_profile:max{}
subscription_sync_total{}	1				subscription_sync_total{}	1
workload:cpu_usage_cores:sum{}	1				workload:cpu_usage_cores:sum{}	1
workload:memory_usage_bytes:sum{}	1			workload:memory_usage_bytes:sum{}	1
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Jira Issue OCPBUGS-61666 has been cloned as Jira Issue OCPBUGS-61698. Will retitle bug to link to clone.
/retitle [release-4.18] OCPBUGS-61698: chore(test/extended/prometheus): bump the series limit of total series sent via telemetry from each cluster

In response to this:

This is an automated cherry-pick of #30249

/assign sdodson

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@sdodson
Copy link
Member

sdodson commented Sep 14, 2025

/skip
/lgtm
/approved
/label backport-risk-assessed

@openshift-ci openshift-ci bot changed the title [release-4.18] OCPBUGS-61666: chore(test/extended/prometheus): bump the series limit of total series sent via telemetry from each cluster [release-4.18] OCPBUGS-61698: chore(test/extended/prometheus): bump the series limit of total series sent via telemetry from each cluster Sep 14, 2025
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Sep 14, 2025
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-61698, which is invalid:

  • expected dependent Jira Issue OCPBUGS-61666 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

This is an automated cherry-pick of #30249

/assign sdodson

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@sdodson
Copy link
Member

sdodson commented Sep 14, 2025

/cherry-pick release-4.17

@openshift-cherrypick-robot
Copy link
Author

@sdodson: once the present PR merges, I will cherry-pick it on top of release-4.17 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.17

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Sep 14, 2025
@sdodson
Copy link
Member

sdodson commented Sep 14, 2025

/test ?

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 14, 2025
Copy link
Contributor

openshift-ci bot commented Sep 14, 2025

@sdodson: The following commands are available to trigger required jobs:

/test e2e-aws-jenkins
/test e2e-aws-ovn-edge-zones
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-image-registry
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial
/test e2e-gcp-ovn
/test e2e-gcp-ovn-builds
/test e2e-gcp-ovn-image-ecosystem
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test images
/test lint
/test okd-scos-images
/test unit
/test verify
/test verify-deps

The following commands are available to trigger optional jobs:

/test e2e-agnostic-ovn-cmd
/test e2e-aws
/test e2e-aws-csi
/test e2e-aws-disruptive
/test e2e-aws-etcd-certrotation
/test e2e-aws-etcd-recovery
/test e2e-aws-ovn
/test e2e-aws-ovn-cgroupsv2
/test e2e-aws-ovn-etcd-scaling
/test e2e-aws-ovn-kube-apiserver-rollout
/test e2e-aws-ovn-kubevirt
/test e2e-aws-ovn-serial-ipsec
/test e2e-aws-ovn-single-node
/test e2e-aws-ovn-single-node-serial
/test e2e-aws-ovn-single-node-techpreview
/test e2e-aws-ovn-single-node-techpreview-serial
/test e2e-aws-ovn-single-node-upgrade
/test e2e-aws-ovn-upgrade
/test e2e-aws-ovn-upgrade-rollback
/test e2e-aws-ovn-upi
/test e2e-aws-ovn-virt-techpreview
/test e2e-aws-proxy
/test e2e-azure
/test e2e-azure-ovn-etcd-scaling
/test e2e-azure-ovn-upgrade
/test e2e-baremetalds-kubevirt
/test e2e-external-aws
/test e2e-external-aws-ccm
/test e2e-external-vsphere-ccm
/test e2e-gcp-csi
/test e2e-gcp-disruptive
/test e2e-gcp-fips-serial
/test e2e-gcp-ovn-etcd-scaling
/test e2e-gcp-ovn-rt-upgrade
/test e2e-gcp-ovn-techpreview
/test e2e-gcp-ovn-techpreview-serial
/test e2e-metal-ipi-ovn
/test e2e-metal-ipi-ovn-dualstack
/test e2e-metal-ipi-ovn-dualstack-bgp-local-gw-techpreview
/test e2e-metal-ipi-ovn-dualstack-bgp-techpreview
/test e2e-metal-ipi-ovn-dualstack-local-gateway
/test e2e-metal-ipi-ovn-kube-apiserver-rollout
/test e2e-metal-ipi-serial
/test e2e-metal-ipi-serial-ovn-ipv6
/test e2e-metal-ipi-virtualmedia
/test e2e-metal-ovn-single-node-live-iso
/test e2e-metal-ovn-single-node-with-worker-live-iso
/test e2e-openstack-ovn
/test e2e-openstack-serial
/test e2e-vsphere
/test e2e-vsphere-ovn-dualstack-primaryv6
/test e2e-vsphere-ovn-etcd-scaling
/test okd-scos-e2e-aws-ovn

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-origin-release-4.18-e2e-agnostic-ovn-cmd
pull-ci-openshift-origin-release-4.18-e2e-aws-csi
pull-ci-openshift-origin-release-4.18-e2e-aws-ovn-cgroupsv2
pull-ci-openshift-origin-release-4.18-e2e-aws-ovn-edge-zones
pull-ci-openshift-origin-release-4.18-e2e-aws-ovn-fips
pull-ci-openshift-origin-release-4.18-e2e-aws-ovn-kube-apiserver-rollout
pull-ci-openshift-origin-release-4.18-e2e-aws-ovn-microshift
pull-ci-openshift-origin-release-4.18-e2e-aws-ovn-microshift-serial
pull-ci-openshift-origin-release-4.18-e2e-aws-ovn-serial
pull-ci-openshift-origin-release-4.18-e2e-aws-ovn-single-node
pull-ci-openshift-origin-release-4.18-e2e-aws-ovn-single-node-serial
pull-ci-openshift-origin-release-4.18-e2e-aws-ovn-single-node-upgrade
pull-ci-openshift-origin-release-4.18-e2e-aws-ovn-upgrade
pull-ci-openshift-origin-release-4.18-e2e-gcp-csi
pull-ci-openshift-origin-release-4.18-e2e-gcp-ovn
pull-ci-openshift-origin-release-4.18-e2e-gcp-ovn-rt-upgrade
pull-ci-openshift-origin-release-4.18-e2e-gcp-ovn-upgrade
pull-ci-openshift-origin-release-4.18-e2e-metal-ipi-ovn
pull-ci-openshift-origin-release-4.18-e2e-metal-ipi-ovn-ipv6
pull-ci-openshift-origin-release-4.18-e2e-metal-ipi-ovn-kube-apiserver-rollout
pull-ci-openshift-origin-release-4.18-e2e-openstack-ovn
pull-ci-openshift-origin-release-4.18-images
pull-ci-openshift-origin-release-4.18-lint
pull-ci-openshift-origin-release-4.18-okd-scos-e2e-aws-ovn
pull-ci-openshift-origin-release-4.18-okd-scos-images
pull-ci-openshift-origin-release-4.18-unit
pull-ci-openshift-origin-release-4.18-verify
pull-ci-openshift-origin-release-4.18-verify-deps

In response to this:

/test ?

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Copy link
Contributor

openshift-ci bot commented Sep 14, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-cherrypick-robot, sdodson
Once this PR has been reviewed and has the lgtm label, please assign simonpasquier for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@sdodson
Copy link
Member

sdodson commented Sep 14, 2025

/test e2e-aws-ovn-single-node-techpreview

@sdodson
Copy link
Member

sdodson commented Sep 14, 2025

/override ci/prow/e2e-gcp-ovn ci/prow/e2e-gcp-ovn-upgrade ci/prow/e2e-aws-ovn-serial ci/prow/e2e-aws-ovn-microshift-serial ci/prow/e2e-aws-ovn-fips

Copy link
Contributor

openshift-ci bot commented Sep 14, 2025

@sdodson: Overrode contexts on behalf of sdodson: ci/prow/e2e-aws-ovn-fips, ci/prow/e2e-aws-ovn-microshift-serial, ci/prow/e2e-aws-ovn-serial, ci/prow/e2e-gcp-ovn, ci/prow/e2e-gcp-ovn-upgrade

In response to this:

/override ci/prow/e2e-gcp-ovn ci/prow/e2e-gcp-ovn-upgrade ci/prow/e2e-aws-ovn-serial ci/prow/e2e-aws-ovn-microshift-serial ci/prow/e2e-aws-ovn-fips

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@sdodson
Copy link
Member

sdodson commented Sep 14, 2025

/override ci/prow/okd-scos-images

Copy link
Contributor

openshift-ci bot commented Sep 14, 2025

@sdodson: Overrode contexts on behalf of sdodson: ci/prow/okd-scos-images

In response to this:

/override ci/prow/okd-scos-images

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@sdodson
Copy link
Member

sdodson commented Sep 15, 2025

/jira refresh

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Sep 15, 2025
@openshift-ci-robot
Copy link

@sdodson: This pull request references Jira Issue OCPBUGS-61698, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.18.z) matches configured target version for branch (4.18.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-61666 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-61666 targets the "4.19.z" version, which is one of the valid target versions: 4.19.0, 4.19.z
  • bug has dependents

Requesting review from QA contact:
/cc @juzhao

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Sep 15, 2025
@openshift-ci openshift-ci bot requested a review from juzhao September 15, 2025 13:33
@sdodson
Copy link
Member

sdodson commented Sep 15, 2025

/test e2e-aws-ovn-single-node-techpreview

@sdodson
Copy link
Member

sdodson commented Sep 15, 2025

/skip
soo soo many e2e jobs

@sdodson
Copy link
Member

sdodson commented Sep 15, 2025

/test e2e-aws-ovn-single-node-techpreview
I didn't expect it to kill off the one I actually requested

@sdodson
Copy link
Member

sdodson commented Sep 15, 2025

/test images

@sdodson
Copy link
Member

sdodson commented Sep 15, 2025

/override ci/prow/e2e-gcp-ovn ci/prow/e2e-gcp-ovn-upgrade ci/prow/e2e-aws-ovn-microshift-serial ci/prow/e2e-aws-ovn-microshift ci/prow/e2e-aws-ovn-fips

Copy link
Contributor

openshift-ci bot commented Sep 15, 2025

@sdodson: Overrode contexts on behalf of sdodson: ci/prow/e2e-aws-ovn-fips, ci/prow/e2e-aws-ovn-microshift, ci/prow/e2e-aws-ovn-microshift-serial, ci/prow/e2e-gcp-ovn, ci/prow/e2e-gcp-ovn-upgrade

In response to this:

/override ci/prow/e2e-gcp-ovn ci/prow/e2e-gcp-ovn-upgrade ci/prow/e2e-aws-ovn-microshift-serial ci/prow/e2e-aws-ovn-microshift ci/prow/e2e-aws-ovn-fips

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@sdodson
Copy link
Member

sdodson commented Sep 15, 2025

/label approved
/verified by reviewing techpreview CI job for failure

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 15, 2025
@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Sep 15, 2025
@openshift-ci-robot
Copy link

@sdodson: This PR has been marked as verified by reviewing techpreview CI job for failure.

In response to this:

/label approved
/verified by reviewing techpreview CI job for failure

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 31dd892 and 2 for PR HEAD 96488de in total

1 similar comment
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 31dd892 and 2 for PR HEAD 96488de in total

@sdodson
Copy link
Member

sdodson commented Sep 16, 2025

/retest-required

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 31dd892 and 2 for PR HEAD 96488de in total

1 similar comment
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 31dd892 and 2 for PR HEAD 96488de in total

Copy link
Contributor

openshift-ci bot commented Sep 16, 2025

@openshift-cherrypick-robot: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-aws-ovn-upgrade 96488de link false /test e2e-aws-ovn-upgrade
ci/prow/e2e-metal-ipi-ovn-kube-apiserver-rollout 96488de link false /test e2e-metal-ipi-ovn-kube-apiserver-rollout
ci/prow/e2e-aws-ovn-cgroupsv2 96488de link false /test e2e-aws-ovn-cgroupsv2
ci/prow/e2e-metal-ipi-ovn-ipv6 96488de link true /test e2e-metal-ipi-ovn-ipv6
ci/prow/e2e-aws-ovn-single-node 96488de link false /test e2e-aws-ovn-single-node
ci/prow/okd-scos-e2e-aws-ovn 96488de link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-ovn-kube-apiserver-rollout 96488de link false /test e2e-aws-ovn-kube-apiserver-rollout
ci/prow/e2e-metal-ipi-ovn 96488de link false /test e2e-metal-ipi-ovn
ci/prow/e2e-aws-ovn-single-node-serial 96488de link false /test e2e-aws-ovn-single-node-serial
ci/prow/e2e-gcp-ovn-rt-upgrade 96488de link false /test e2e-gcp-ovn-rt-upgrade
ci/prow/e2e-agnostic-ovn-cmd 96488de link false /test e2e-agnostic-ovn-cmd
ci/prow/e2e-aws-ovn-single-node-upgrade 96488de link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-gcp-csi 96488de link false /test e2e-gcp-csi
ci/prow/e2e-openstack-ovn 96488de link false /test e2e-openstack-ovn
ci/prow/e2e-aws-ovn-edge-zones 96488de link true /test e2e-aws-ovn-edge-zones
ci/prow/e2e-aws-csi 96488de link false /test e2e-aws-csi

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 31dd892 and 2 for PR HEAD 96488de in total

@sdodson
Copy link
Member

sdodson commented Sep 16, 2025

/override ci/prow/e2e-aws-ovn-serial

@sdodson sdodson merged commit 7aabb3c into openshift:release-4.18 Sep 16, 2025
28 of 30 checks passed
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Jira Issue Verification Checks: Jira Issue OCPBUGS-61698
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-61698 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

In response to this:

This is an automated cherry-pick of #30249

/assign sdodson

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

Copy link
Contributor

openshift-ci bot commented Sep 16, 2025

@sdodson: Overrode contexts on behalf of sdodson: ci/prow/e2e-aws-ovn-serial

In response to this:

/override ci/prow/e2e-aws-ovn-serial

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-cherrypick-robot
Copy link
Author

@sdodson: #30253 failed to apply on top of branch "release-4.17":

Applying: chore(test/extended/prometheus): bump the series limit of total series sent via telemetry from each cluster
Using index info to reconstruct a base tree...
M	test/extended/prometheus/prometheus.go
Falling back to patching base and 3-way merge...
Auto-merging test/extended/prometheus/prometheus.go
CONFLICT (content): Merge conflict in test/extended/prometheus/prometheus.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 chore(test/extended/prometheus): bump the series limit of total series sent via telemetry from each cluster

In response to this:

/cherry-pick release-4.17

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-tests
This PR has been included in build openshift-enterprise-tests-container-v4.18.0-202509161903.p0.g7aabb3c.assembly.stream.el9.
All builds following this will include this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria
Projects
None yet
Development

Successfully merging this pull request may close these issues.